Deleting DOORS Users

A customer wants to delete old, unused users from their DOORS db. They're asking if there are any gotchas with simply going in and deleting them. For example, would any views or other information be affected. I don't see much in the help about the effects of a user delete.

Can you let me know if user deletions are reasonably straightforward or if there are things the customer has to do prior to deleting them. If there's documentation that addresses this, please point to me to same.

Thanks


suvamara - Mon Feb 16 16:19:35 EST 2015

Re: Deleting DOORS Users
kourosh - Mon Feb 16 17:52:46 EST 2015

Thses are all things to consider:

  • If a user you deleted had private views, the only other user who will be able to Access these views once the user is deleted is the actual 'Administrator' account.
  • History entries in modules associated with that user will now show up as "Read locked data" and can only be viewable by the 'Administrator' account.
  • And if there are modules where only that user had access to, they might now have to be modified by the 'Administrator' account so others can access them.

You can also simply 'disable' a user account rather than delete it.

Re: Deleting DOORS Users
suvamara - Mon Feb 16 18:03:41 EST 2015

kourosh - Mon Feb 16 17:52:46 EST 2015

Thses are all things to consider:

  • If a user you deleted had private views, the only other user who will be able to Access these views once the user is deleted is the actual 'Administrator' account.
  • History entries in modules associated with that user will now show up as "Read locked data" and can only be viewable by the 'Administrator' account.
  • And if there are modules where only that user had access to, they might now have to be modified by the 'Administrator' account so others can access them.

You can also simply 'disable' a user account rather than delete it.

Thanks @kourosh. This is very helpful.

Re: Deleting DOORS Users
llandale - Thu May 28 17:05:34 EDT 2015

kourosh - Mon Feb 16 17:52:46 EST 2015

Thses are all things to consider:

  • If a user you deleted had private views, the only other user who will be able to Access these views once the user is deleted is the actual 'Administrator' account.
  • History entries in modules associated with that user will now show up as "Read locked data" and can only be viewable by the 'Administrator' account.
  • And if there are modules where only that user had access to, they might now have to be modified by the 'Administrator' account so others can access them.

You can also simply 'disable' a user account rather than delete it.

If the DOORS user represents a human who no longer should access DOORS, I'd be tempted to rename that user to something like "Removed-003" and erase the "System User name"; then disable.  This makes it far easier when you see something with access issues (a private view) to be able to take action.  If you are the Administrator then straighten out the access; if a DB admin then enable the user, give it a temp password, log in as that user, and take care of it.

-Louie

You need a batch background snooper looking for stuff lacking any RMCDA access; particularly views.

Re: Deleting DOORS Users
TheRat - Mon Jun 01 02:26:09 EDT 2015

You also have to be careful of any attributes of type "Username" in modules - any entries with the values of deleted users will be blanked.  At one stage that was also true for baselines, but that may have been fixed.

Re: Deleting DOORS Users
llandale - Mon Jun 01 19:49:13 EDT 2015

llandale - Thu May 28 17:05:34 EDT 2015

If the DOORS user represents a human who no longer should access DOORS, I'd be tempted to rename that user to something like "Removed-003" and erase the "System User name"; then disable.  This makes it far easier when you see something with access issues (a private view) to be able to take action.  If you are the Administrator then straighten out the access; if a DB admin then enable the user, give it a temp password, log in as that user, and take care of it.

-Louie

You need a batch background snooper looking for stuff lacking any RMCDA access; particularly views.

... put the original name of the user in the comments field.